◀ Prev • Parts • Full • Next ▶

This section covers the protocol itself: implementations, transport interfaces, application-layer protocols built on top, and low-level network utilities.

See Implementations for the full list of Reticulum implementations. Embedded/firmware implementations for specific hardware are covered under Custom Firmware, since they're typically encountered as something you flash rather than something you install.

• BLEInterface – BLE interface for Linux systems.

• FreeDVInterface – Plug and play, cross-platform sound modem interface for HF radios using the FreeDV API.

• Meshtastic_Interface – Interface for using Meshtastic as the underlying networking layer.

• Modem73Interface – Interface for modem73. Enables any HF/VHF/UHF radio to operate with Reticulum.

• RNodeTCPInterface – A modified version of RNodeInterface that supports TCP connections only.

• SX126xInterface – Drives SX1262 LoRa chips directly over SPI on Linux SBCs. No RNode needed.

• retiqr – An alternative reticulum QR + USB HID interface (via TCPClientInterface).

• RNS-over-HTTP – Tunnels traffic over standard HTTP/S POST requests (via PipeInterface).

• LXMF – Very flexible and extensible messaging protocol with support for voice messages, image messages, file attachments and more.

• LXMF-rs – A Rust implementation of LXMF. Untested, incomplete, use with caution.

• LXMF-swift – Swift implementation of LXMF messaging for Reticulum networks.

• LXMF-PHP – A universal, distributed and secure messaging protocol for Reticulum ported to PHP.

• microLXMF - LXMF implementation in C++, used by Pyxis.

• LXST – Real-time, general purpose voice and signals transport protocol with built-in telephony primitives.

• LXST-kt – A re-implementation of LXST in Kotlin, built for native Android.

• LXST-swift – Swift implementation of LXST voice calls for Reticulum networks.

• LRGP-rs and LRGP-py – Lightweight Reticulum Gaming Protocol. Multiplayer games over LXMF/Reticulum mesh networks.

• LXCF – Lightweight eXtensible CHANNEL Format — an IRC-style semantic layer / protocol over LXMF and Reticulum.

• POPR – Reticulum LXM distribution based on Post Office Protocol.

• RDNS – A decentralized DNS-esque system, WIP.

• Akita DDNS – Akita DDNS is a robust, decentralized, and dynamic destination naming system (DDNS) built specifically for the Reticulum Network Stack. It provides a resilient alternative to traditional centralized DNS for mapping human-readable names to dynamic Reticulum identities (RIDs) within a mesh network.

• RRC – Reticulum Relay Chat.

• RMAP – Community-provided world map with publicly accessible Reticulum nodes and access points.

• Reticulum Interface Directory – Auto-discovered and user-submitted public Reticulum transport nodes.

• Reticulum Node Reliability Tracking – A public canary that continuously probes Reticulum Backbone nodes, scores their reliability, and exposes the data so the community can make informed routing decisions.

• RNS Mesh Observer – Real-time Reticulum network observer: REST + WebSocket API for mesh topology and peer tracking.

• RNS Map – Live Reticulum network visualiser — dartboard map of LXMF, Nomadnet and propagation nodes over LoRa.

◀ Prev • Parts • Full • Next ▶